Systems and methods for managing building signature intelligent electronic devices

ABSTRACT

A method for evaluating a building signature operational model (BSOM) associated with a building signature intelligent electronic device (BSIED) includes processing building signature operational data (BSOD) on a cloud-connected central processing unit to identify the BSIED from which the BSOD was received, and to determine if a current BSOM associated with the BSIED, and used by the BSIED to generate the BSOD, needs to be updated. In response to determining that the current BSOM needs to be updated, a new BSOM is selected for the BSIED from a BSOM library based, at least in part, on one or more characteristics associated with the BSIED. The new BSOM is transmitted to the BSIED for installation on the BSIED.

BACKGROUND

Monitoring and control devices are used in a wide variety ofinstallations, such as industrial facilities, warehouses, officebuildings or other commercial complexes, data centers, powerdistribution networks, and the like. These devices monitor conditions inthe installation, such as temperature, power usage, power quality, etc.,and provide indications of the monitored parameters that can be used tocontrol conditions within the installation. Examples of monitoring andcontrol devices include smart utility meters, power quality meters, andother embedded systems. The software for monitoring and control devicestypically includes low-level firmware containing various operation andcontrol functions. For example, firmware may enable integration orcommunication between hardware components that are not otherwise able tocommunicate. Firmware typically requires significant testing anddevice-specific expertise to be developed and deployed effectively.Installing new firmware on a monitoring and control device oftennecessitates that the device be shut down or disabled throughout theinstallation process. Installing new firmware may further require adevice-specific expert to be deployed on site and manually perform someor all of the installation process. Installing new firmware may alsoincur the risk of introducing undetected software errors that couldimpact the operation of the device in unanticipated ways.

SUMMARY

Described herein are systems and methods related to building signatureintelligent electronic devices (BSIEDs) and building signature systemsincluding BSIEDs. More particularly, in one aspect, a method forevaluating a building signature operational model (BSOM) associated witha BSIED includes: receiving building signature input data (BSID) fromone or more building signature data sources (BSDSs) at an input of theBSIED, and processing the received BSID using a current BSOM stored on amemory device of the BSIED to generate building signature operationaldata (BSOD). In embodiments, the BSOD corresponds to a quantitypredicted by the BSOM, for example, building energy consumption.

The method also includes: transmitting the BSOD to a cloud-connectedcentral processing unit communicatively coupled to the at least oneBSIED, processing the BSOD on the cloud-connected central processingunit to identify the BSIED, and processing the BSOD to determine if thecurrent BSOM associated with the BSIED needs to be updated. In responseto determining that the current BSOM needs to be updated, a new BSOM isselected for the BSIED based, at least in part, on one or morecharacteristics associated with the BSIED. The new BSOM is transmittedto the BSIED for installation on the BSIED. The BSOM, which is oneexample type of operational model, may be used, for example, to monitorand predict energy consumption of a building in which the BSIED isinstalled. More particularly, the BSIED may be coupled to receive BSIDat BSIED inputs and, using the BSOM, the BSIED may be configured togenerate BSOD indicative of building energy consumption at an outputthereof. In embodiments, the BSID may include production activity data(e.g., from equipment in the building), weather data, occupancy data,and other driver data that may be suitable for use with the BSOM (whichis device and building specific), as will be described in greater detailbelow.

In some embodiments, the term “building signature” as used herein refersto building energy consumption signature. Additionally, in someembodiments the term “signature” as used herein refers to the responsefunction of energy consumption in a building to various input (or“driver”) variables that influence energy consumption.

The method for evaluating the BSOM associated with the BSIED may includeone or more of the following features either individually or incombination with other features. The method may further includevalidating that the new BSOM was correctly transmitted to the BSIED. Themethod may further include processing BSID (e.g., on the cloud, or onthe BSIED) using the new BSOM to generate BSOD associated with the newBSOM, and evaluating accuracy of the BSOD to confirm that the new BSOMis operating as expected. The BSID may be received from one or moreBSDSs at an input of the BSIED. The BSOD may be generated at an outputof the BSIED. The BSDSs may include equipment to which the BSIED iscoupled. The BSID may include energy usage information associated withthe BSDSs. The BSID may correspond to test BSID (e.g., historical BSID)for validating accuracy of the BSOM. In some embodiments, the test BSIDmay be retrieved from a memory device of the BSIED. Additionally, insome embodiments the test BSID may be retrieved from a memory deviceassociated with the cloud-connected central processing unit.

Processing BSOD on a cloud-connected central processing unit to identifythe BSIED from which the BSOD was received from, and to determine if acurrent BSOM associated with the BSIED needs to be updated, may includedetermining if a predetermined time period or other predeterminedcondition has occurred since the current BSOM has last been updated orverified. In response to determining that the predetermined time periodor other predetermined condition has occurred, a request signal may besubmitted to the BSIED for retrieving BSOD from the BSIED. In responseto receiving the request signal, the BSIED may transmit BSOD to thecloud-connected central processing unit. The cloud-connected centralprocessing unit may process the BSOD to identify the BSIED from whichthe BSOD was received from, and to determine if a current BSOMassociated with the BSIED needs to be updated.

Processing BSOD on a cloud-connected central processing unit todetermine if a current BSOM associated with the BSIED needs to beupdated may include: comparing a version number of an algorithm used togenerate the current BSOM with a version number of a latest modelgenerating algorithm, and determining that the current BSOM needs to beupdated if the version number of the algorithm used to generate thecurrent BSOM is substantially different from the version number of thelatest model generating algorithm (e.g., by more than few versions).

Selecting a new BSOM for the BSIED may include generating a new BSOM forthe BSIED based, at least in part, on the BSOD and one or morecharacteristics associated with the BSIED. Selecting the new BSOM forthe BSIED may include selecting a closest BSOM for the BSIED from a BSOMlibrary based, at least in part, on one or more characteristicsassociated with the BSIED. Selecting the new BSOM for the BSIED may alsoinclude determining if the closest BSOM needs to be translated orotherwise modified to work with the BSIED. In response to determiningthat the closest BSOM needs to be translated or otherwise modified towork with the BSIED, the closest BSOM may be translated into a form theBSIED supports. The translated BSOM may be selected as the new BSOM forthe BSIED.

The BSOM library may be stored on a memory device associated with thecloud-connected central processing unit. The BSOM library may include aplurality of BSOMs. The plurality of BSOMs may be generated by thecloud-connected central processing unit in response to receiving inputdata from one or more respective data sources associated with the BSIEDsfor which the plurality of BSOMs are intended. The data sources mayinclude at least one of a temperature sensor, a humidity sensor, and anoccupancy sensor configured to generate respective temperature, humidityand occupancy input data pertaining to the environment(s) in which theBSIEDs are installed.

The characteristics associated with the BSIED in selecting the new BSOMfor the BSIED may include BSIED type, BSIED complexity, and/or buildingsignature parameters monitored by the BSIED. The BSIED type may includeat least one of an energy meter, a power quality monitor, a waveformmonitor, a programmable sensing device, a measurement and verificationdevice, an uninterruptible power supply, a power quality correctiondevice, and a harmonic filter with metering capabilities. The buildingsignature parameters monitored by the BSIED may include one or moreenergy consumption parameters. Typical energy consumption parameters, or“drivers,” include, but are not limited to: outdoor weather temperature,number of occupants on a given day, production activity metrics specificto the activity (or activities) in the building (e.g., unitsmanufactured in a manufacturing business), hours of sunlight per day,wind speed, and relative humidity.

The BSOD generated by the BSIED using the BSOM may be indicative of anestimated energy consumption of a building in which the BSIED may beinstalled. The BSIED complexity may be selected from “basic”,“intermediate”, and “advanced”. An intermediate complexity BSIED mayhave more functionality than a basic complexity BSIED. An advancedcomplexity BSIED may have more functionality than the intermediatecomplexity BSIED. The intermediate complexity BSIED may be responsive tomore building signature data sources than the basic complexity BSIED.The advanced complexity BSIED may be responsive to more buildingsignature data sources and may support more complex BSOM calculationsthan the intermediate complexity BSIED.

The method may further include subsequent to selecting the new BSOM forthe BSIED, determining if the current BSOM is capable of being updatedto the new BSOM. In response to determining that the current BSOM iscapable of being updated to the new BSOM, parameters to be added to,removed from and/or modified in the current BSOM may be identified toupdate the current BSOM to the new BSOM. The current BSOM may be to thenew BSOM based on the identified parameters.

Updating the current BSOM to the new BSOM may include generating theparameters identified to be added to and/or modified in the currentBSOM. Transmitting the new BSOM to the BSIED may include: (a)transmitting the generated parameters to the BSIED, (b) providing anindication of which parameters, if any, should be removed from thecurrent BSOM to the BSIED, and (c) updating the current BSOM to the newBSOM on the BSIED based on the generated parameters and the providedindication.

The method may further include tuning the new BSOM in response to userinput, for example, received from a user input device. In someembodiments, the new BSOM is tuned on the BSIED. In other embodiments,the new BSOM is tuned on the cloud-connected central processing unit.

In embodiments, a building signature system is also provided herein. Thebuilding signature system includes at least one building signatureintelligent electronic device (BSIED) comprising a memory device and aprocessor coupled to the memory device. The processor and the memorydevice are configured to receive building signature input data (BSID)from one or more building signature data sources (BSDSs). The processorand the memory device are also configured to process the received BSIDusing a current building signature operational model (BSOM) stored onthe memory device to generate building signature operational data(BSOD). The processor and the memory device are further configured totransmit the BSOD to a cloud-connected central processing unitcommunicatively coupled to the at least one BSIED.

The cloud-connected central processing unit is configured to process theBSOD to identify the at least one BSIED from which the BSOD was receivedfrom, and to determine if the current BSOM associated with the at leastone BSIED needs to be updated. In response to determining that thecurrent BSOM needs to be updated, a new BSOM for the at least one BSIEDmay be selected based, at least in part, on one or more characteristicsassociated with the at least one BSIED. In embodiments, the new BSOM isselected from a BSOM library. The new BSOM may be transmitted to the atleast one BSIED for installation on the at least one BSIED. Inembodiments, the BSDSs may include equipment to which the at least oneBSIED is coupled, and the BSID comprises energy usage informationassociated with the BSDSs. Additionally, in embodiments the BSOD may beindicative of an estimated energy consumption of a building in which theat least one BSIED is installed.

Aspects and embodiments provide BSIEDs capable of executingapplications-level software programs (“applications”), and methods fordynamically and automatically reprogramming these devices withoutrequiring manual firmware updates.

Certain applications executed on a BSIED involve gathering externaldata, controlling one or more external devices, or performing analyticson the fly or on internally-stored data. For monitoring and controldevices, gathering external data may include monitoring one or moreparameters associated with an installation in which the BSIED islocated. The building signature operational model BSOM of a BSIED mayinclude one or more applications, and may be improved by updating theBSIED with new application instruction sets and/or new data parametersto be referenced by those instruction sets. However, updating theapplications on a BSIED has conventionally involved deploying an expertto manually update the entire device firmware, and is therefore costlyin terms of both time and money. Accordingly, aspects and embodimentsare directed to methods and apparatus for automatically generatingimproved BSOMs for BSIEDs and automatically updating those BSIEDs withthe new BSOMs, without requiring burdensome firmware updates.

In embodiments, each BSOM is compatible with certain BSIEDs and includesone or more applications, software instructions, algorithms, functions,or software parameters, which may be arranged in one or morehierarchies. The BSIEDs may be configured to gather and transmitoperational data to one or more cloud-connected central processingunits. The cloud connected central-processing units may execute cloudanalytic models configured to analyze operational data, for exampleusing regression analysis. Cloud analytic models may also involveaccessing and analyzing one or more sources of stored or external data.Cloud analytic models may further be configured to develop new BSOMsbased on the analysis and transmit the new BSOMs to compatible BSIEDs.Compatible BSIEDs may be able to install the new BSOMs without requiringa firmware upgrade or, for example, without requiring downtime or manualhuman interaction.

According to one embodiment, there is provided a system for generating anew BSOM for BSIED and reprogramming the BSIED to execute the new BSOM.The system may comprise a first BSIED including a BSIED processorconfigured to execute instructions corresponding to a BSOM, collectdata, and encode the data, a BSIED memory containing the BSOM includinga set of application instructions and a set of application parameters,and configured to store the encoded data, a BSIED communications modulecommunicatively coupled to a cloud and configured to send the encodeddata to the cloud. The system may further comprise a cloud computersystem including a cloud communications module communicatively coupledto the cloud, and a cloud processor configured to receive identificationinformation of the first BSIED via the cloud communications module,receive the encoded data from the first BSIED via the cloudcommunications module, select a cloud analytic model responsive toreceiving the identification information from the first BSIED, decodethe encoded data into decoded data via the cloud analytic model, analyzethe decoded data via the cloud analytic model, and generate, responsiveto analyzing the decoded data via the cloud analytic model, anapplication-based BSOM.

In one example the cloud processor is further configured to transmit theapplication-based BSOM to the first BSIED via the cloud communicationsmodule. The cloud processor may be further configured to transmit theapplication-based BSOM to a second BSIED via the cloud communicationsmodule, wherein the second BSIED shares at least one of a model, type,location, owner, operator, hardware configuration, or softwareconfiguration with the first BSIED. The data collected by the firstand/or second BSIED may include values of at least one environmentalparameter sensed by at least one a sensor of the BSIED.

Various embodiments herein describe methods for reprogramming a BSIED toexecute a BSOM. The method may include transmitting, via acommunications module coupled to a processor of the BSIED, operationaldata from the BSIED to a cloud-connected central processing unit;analyzing the operational data using a cloud analytic model executed bythe central processing unit; responsive to the analyzing, generating theBSOM; receiving at the BSIED, via the communications module, the BSOMfrom the central processing unit; and responsive to receiving the BSOMat the BSIED, installing the BSOM on the BSIED and reprogramming theBSIED to execute the BSOM.

In various embodiments of the method for reprogramming, the BSIED mayinclude one or more of an energy meter, a power quality monitor, awaveform monitor, a programmable sensing device, an uninterruptiblepower supply, a power quality correction device, or a harmonic filterwith metering capabilities. The method may further include receiving atthe central processing unit at least one external data set, whereinanalyzing the operational data includes analyzing the at least oneexternal data set. The at least one external data set includes at leastone of weather data and utility pricing data. In certain embodiments ofthe method, analyzing an operational data set may include performing aregression analysis, or other recursive or iterative analysis.Reprogramming a BSIED to execute the BSOM may include modifying at leastone application stored on a BSIED memory coupled to the processor of theBSIED. Reprogramming the BSIED to execute the BSOM may also includemodifying at least one application instruction or at least oneapplication parameter stored on a BSIED memory coupled to the processorof the BSIED.

Other embodiments described herein describe a method for generating anew BSOM for a BSIED. The method may include receiving at acloud-connected central processing unit, via a communications modulecoupled to the cloud-connected central processing unit, at least oneencoded data set generated by a first BSIED pursuant to an existing BSOMexecuting on the first BSIED; receiving at the cloud-connected centralprocessing unit, via the communications module, identificationinformation associated with the first BSIED; decoding with thecloud-connected central processing unit the at least one encoded dataset to produce a corresponding at least one decoded data set; selectingwith the cloud-connected central processing unit a cloud analytic modelassociated with the first BSIED responsive to receiving theidentification information associated with the first BSIED; analyzing,via the cloud analytic model, the at least one decoded data set; andgenerating, responsive to analyzing the at least one decoded data set,the new BSOM.

The method for generating may include receiving the identificationinformation includes receiving at least one of a type of the firstBSIED, a unique identifier of the first BSIED, an identity of an owneror operator of the first BSIED, a location of the first BSIED, ahardware configuration of the first BSIED, and a software configurationof the first BSIED. The method may also include transmitting the newBSOM from the cloud-connected central processing unit to the firstBSIED. The method may further include receiving at the cloud-connectedcentral processing unit, via the communications module, additionalidentification information associated with a second BSIED; anddetermining whether the second BSIED is associated with the cloudanalytic model responsive to the additional identification information.In various additional embodiments, the method includes, responsive todetermining that the second BSIED is associated with the cloud analyticmodel, generating the new BSOM includes generating the new BSOM capableof executing on the second BSIED, and further including transmitting thenew BSOM from the cloud-connected central processing unit to the secondBSIED. The method may further comprise storing, via a memory modulecoupled to the cloud-connected central processing unit, the at least oneencoded data set. In some embodiments, the method also includesreceiving at the cloud-connected central processing unit additional datafrom a cloud-connected data source, wherein generating the new BSOMincludes generating the new BSOM responsive to analyzing the at leastone decoded data set and the additional data.

Further embodiments herein describe a system for generating a new BSOMfor BSIED comprising: the BSIED including a processor, a communicationsmodule, and a memory, the BSIED configured to produce operational data;and a cloud-connected central processing unit coupled to the BSIED viathe communications module and a cloud network, the central processingunit configured to receive the operational data from the BSIED via thecommunications module, to analyze the operational data according to acloud analytic model, and to generate the new operational model based onanalyzing the operational data, the central processing unit beingfurther configured to automatically transmit the new BSOM to the BSIEDvia the communications module, and the BSIED being further configured toautomatically install and execute the new BSOM received from the centralprocessing unit using the memory and the processor. The BSIED mayinclude one or more of an energy meter, a power quality monitor, awaveform monitor, a programmable sensing device, an uninterruptiblepower supply, a power quality correction device, and a harmonic filterwith metering capabilities. The central processing unit may be furtherconfigured to receive from the BSIED identification informationassociated with the BSIED and to select the cloud analytic model basedon the identification information. The BSIED identification informationmay include at least one of a type of the first BSIED, a uniqueidentifier of the first BSIED, an identity of owner or operator of thefirst BSIED, a location of the first BSIED, a hardware configuration ofthe first BSIED, and a software configuration of the first BSIED.

In various addition embodiments of the system, the BSOD produced by theBSIED includes an encoded data set, and the central processing unit ofthe system may be configured to receive and decode the encoded data set.The central processing unit may further be configured to receive atleast one additional data set from a cloud-connected source, to analyzethe at least one additional data set according to the cloud analyticmodel, and to generate the new BSOM based on analyzing both the BSOD andthe at least one additional data set. The at least one additional dataset may include at least one of weather data and utility pricing data.The central processing unit may also be configured to perform aregression analysis on the BSOD.

These exemplary aspects, examples, and embodiments are discussed indetail below, along with other aspects, examples, embodiments, andadvantages. Examples and embodiments disclosed herein may be combinedwith other examples or embodiments in any manner consistent with atleast one of the principles disclosed herein, and references to “anexample,” “some examples,” “an alternate example,” “various examples,”“one example”, “implementations”, “embodiments”, or the like are notnecessarily mutually exclusive and are intended to indicate that aparticular feature, structure, or characteristic described may beincluded in one or more examples or implementations. The appearances ofsuch terms herein are not necessarily all referring to the same exampleor implementation. Various aspects, examples described herein mayinclude means for performing any of the described methods or functions.

BRIEF DESCRIPTION OF THE DRAWINGS

The foregoing features of the disclosure, as well as the disclosureitself may be more fully understood from the following description ofthe drawings, in which:

FIG. 1 is a block diagram illustrating an example building signaturesystem in accordance with embodiments of the disclosure;

FIG. 2 is a block diagram illustrating an example building signatureintelligent electronic device (BSIED) that may be used in a buildingsignature system in accordance with embodiments of the disclosure;

FIG. 3 is a block diagram illustrating an example building associatedwith a building signature system in accordance with embodiments of thedisclosure, the building having a plurality of BSIEDs installed therein;

FIG. 4 is a flowchart illustrating an example method for evaluating abuilding signature operational model (BSOM) associated with a BSIED inaccordance with embodiments of the disclosure;

FIG. 5 is a flowchart illustrating an example method for identifying aBSIED from building signature operational data (BSOD);

FIG. 6 is a flowchart illustrating an example method for determining ifa BSOM associated with a BSIED needs to be updated;

FIG. 7 is a flowchart illustrating an example method for determining ifa BSOM associated with a BSIED needs to be updated;

FIG. 8 is a flowchart illustrating an example method for selecting a newBSOM for a BSIED;

FIG. 9 is a flowchart illustrating an example method for determining ifBSOD generated by a BSIED should be processed locally or in the cloud;

FIG. 10 is a plot showing example BSOD generated by a BSIED; and

FIG. 11 is a plot showing further example BSOD generated by a BSIED.

DETAILED DESCRIPTION

There are many circumstances in which it is desirable to monitor certainparameters, and to track patterns of such parameters. For example, itcan be desirable to monitor energy usage parameters within aninstallation, and to track patterns of the energy usage over time.According to certain aspects and embodiments, tracking patterns of oneor more parameters (for example energy parameters) and taking someaction based on detected patterns (e.g., providing a control signal toan external device or providing an alert) can be accomplished directlywithin a monitoring and control device or by sending data to a centralprocessing unit connected to the device. Conventional monitoring andcontrol devices can be used for simple energy (or other) parametertracking and providing responsive alerts. However, the capabilities ofconventional monitoring and control devices are generally limited todetecting and reacting to patterns of monitored parameters. Althoughfixed or relative set-points can be established in conventional devicesand used to provide alerts when the set-points are exceeded, forexample, the configuration of these set-points typically must beconfigured manually for each device. This manual reconfiguration can betime-consuming and expensive, particularly if the set-pointconfigurations are part of the device firmware.

Aspects and embodiments provide a dynamic monitoring and controlmethodology that leverages enhanced computing capability of servers orother computing devices that can be connected to a target monitoring andcontrol device, along with an ability to provide application-level(rather than firmware-level) programming to the target device and todynamically update the programming based on monitored parameters orexternal data. As discussed in more detail below, certain aspects andembodiments are directed to automatic creation of application-levelprograms for building signature intelligent electronic devices (BSIEDs),including certain monitoring and control devices; the programs beingconfigured to detect a pattern of interest in one or more monitoredparameters based on analysis that can be performed by a centralprocessing unit connected to the intelligent electronic device. Eachprogram can be configured to match the capabilities of the targetintelligent electronic device, as discussed further below. In addition,aspects and embodiments provide for automatic delivery of a generatedprogram to the target device, and dynamic updating or reconfiguration ofthe program based on continuing analysis of data collected by the targetdevice. An updated BSIED may also execute instructions that utilizeexisting data previously stored on the device prior to the update.

It is to be appreciated that examples of the methods and apparatusesdiscussed herein are not limited in application to the details ofconstruction and the arrangement of components set forth in thefollowing description or illustrated in the accompanying drawings. Themethods and apparatuses are capable of implementation in other examplesand of being practiced or of being carried out in various ways. Examplesof specific implementations are provided herein for illustrativepurposes only and are not intended to be limiting. Also, the phraseologyand terminology used herein is for the purpose of description and shouldnot be regarded as limiting. The use herein of “including,”“comprising,” “having,” “containing,” “involving,” and variationsthereof is meant to encompass the items listed thereafter andequivalents thereof as well as additional items. References to “or” maybe construed as inclusive so that any terms described using “or” mayindicate any of a single, more than one, and all of the described terms.

A BSIED is a computational electronic device optimized to perform aparticular function or set of functions. As discussed above, examples ofBSIEDs include monitoring and control devices, such as, but not limitedto, energy parameter monitoring devices. BSIEDs may be used to performmonitoring and control functions in a wide variety of installations. Theinstallations may include industrial facilities, warehouses, officebuildings or other commercial complexes, computing co-location centers,data centers, power distribution networks, and the like. For example,where the BSIED is an electrical power monitoring device, it may becoupled to an electrical power distribution system and configured tosense and store data representing operating characteristics (e.g.,voltage, current, waveform distortion, power, etc.) of the powerdistribution system. These characteristics may be analyzed by a user toevaluate potential performance or power quality-related issues. TheBSIED may include a controller (which in certain BSIEDs can beconfigured to run one or more applications), firmware, a memory, acommunications interface, and connectors that connect the BSIED toexternal systems or devices. At least certain aspects of the monitoringand control functionality of a BSIED may be embodied in a computerprogram that is accessible by the BSIED.

Certain BSIEDs possess sufficient resources to execute higher-levelsoftware applications built atop the firmware and enabling the BSIED toperform more generalized or advanced functions. Firmware is relativelylow-level software designed to permit one or more hardware components ina BSIED to communicate with each other and to permit higher-levelapplication software to be executable on one or more hardware componentssuch as processors. The firmware generally includes machine instructionsfor directing the controller of the BSIED to carry out operationsrequired for the BSIED. In contrast, applications are higher-levelsoftware that typically rely upon firmware in order to be executable ona particular device. Applications comprise bundles of softwareinstructions stored in memory that use and access one or more dataparameters also stored in memory. Applications may be written in adifferent programming language than that used for firmware programming,thus requiring intermediate software such as compilers or assemblers totranslate between application instructions and firmware instructions andvice versa. As discussed above, updating BSIED firmware is considered a“heavy” process for a number of reasons. First, the installation of newfirmware often requires the device being updated to be powered off orotherwise disabled throughout the update process. Second, all or part ofa BSIED firmware installation must often be performed manually. Forexample, a human installer may be required to interact with one or morephysical buttons or interfaces on the BSIED throughout the installationprocess. The installer may further be required to connect one or moresources of external media to the BSIED in order to transfer one or morefiles associated with the firmware update.

A BSIED can be configured to perform one or more monitoring, control,and/or analysis functions pursuant to its one or more associatedbuilding signature operational models (BSOMs). A BSEID could for examplerun one BSOM to predict energy consumption and simultaneously run aseparate and independent BSOM to predict responses to power qualityproblems. As used herein, the term “building signature operationalmodel” refers to a set of application instructions and/or applicationdata parameters stored in the BSIED memory and configured to execute ina particular manner. The set of applications comprising a BSIEDoperational model can be configured to work together in order toimplement one or more BSIED monitoring, control, and/or analysisfunctions. The execution of an operational model results in operationaldata being collected and/or generated in the BSIED's memory. Thisoperational data may include measurement data corresponding to one ormore monitored parameters, and/or other data. According to variousembodiments, the operational model of a BSIED, including one or moreapplications, application instructions, and/or data parameters, may beupdated or modified without needing to suspend or modify the firmware.In certain embodiments, other applications not associated with theapplications being modified may continue to function. In someembodiments, updating of the building signature operational model can beperformed automatically on the BSIED, without the need for a human beingto be dispatched to the location of the BSIED or to manually interactwith the device.

Examples of the BSIEDs can include, but are not limited to, smart powermeters, PowerLogic ION series meters or Sepam Protection Relays, both ofwhich are manufactured by Schneider Electric, measurement andverification devices, and/or other programmable electronic devices.Further examples of BSIED are discussed in connection with figuresbelow.

In some embodiments, the term “BSIED” as used herein may refer to ahierarchy of BSIEDs operating in tandem. For example, a BSIED maycorrespond to a hierarchy of energy meters, power meters, or other typesof resource meters. The hierarchy may comprise a tree-based hierarchy,such a binary tree, a tree having one or more child nodes descendingfrom each parent node, or combinations thereof, wherein each noderepresents a specific BSIED. In some instances, the hierarchy of BSIEDsmay share data or hardware resources and may execute shared software.

In some embodiments, the term “BSOM” as used herein may refer to ahierarchy of BSOMs executing in tandem. The hierarchy may comprise atree-based hierarchy, such a binary tree, a tree having one or morechild nodes descending from each parent node, or combinations thereof,wherein each node represents a specific function, algorithm,instruction, application, or parameter.

Referring to FIG. 1, an example building signature system in accordancewith embodiments of the disclosure includes a plurality of buildingsignature intelligent electronic devices (BSIEDs) 111, 112, 113, 114capable of sensing or monitoring one or more building signatureparameters (e.g., energy usage parameters) associated with buildings101, 102 in which the BSIEDs 111, 112, 113, 114 are installed. In theexample embodiment shown, BSIED 111 is installed in building 101.Additionally, in the example embodiment shown BSIEDs 112, 113, 114 areinstalled in building 102. In embodiments, any number of BSIEDs may beinstalled in each of the buildings 101, 102. The buildings 101, 102 maycorrespond, for example, to commercial, industrial or institutionalbuildings.

As shown in FIG. 1, the building signature system also includes aplurality of sensors 131, 132 that may be used in connection with theBSIEDs 111, 112, 113, 114, for example, to increase the accuracy ofoutputs signals (e.g., building signature operational data (BSOD))generated by the BSIEDs 111, 112, 113, 114, as will be discussed furtherbelow. Each of the BSIEDs 111, 112, 113, 114 has one or more associatedbuilding signature operational models (BSOMs) that by the BSIEDs 111,112, 113, 114 to generate BSIED output signals, specifically BSOD. TheBSOMs may, for example, be used to predict the consumption of thebuildings in which the BSIEDs 111, 112, 113, 114 are installed (here,buildings 101, 102) building given one or more associated buildingsignature inputs (e.g., environmental inputs, such as weather,occupancy, and production activity).

In embodiments, sensor 131 may correspond to a local sensor that isinstalled in building 102. Additionally, in embodiments sensor 132 maycorrespond to a local sensor that is installed proximate to (e.g.,within a predetermined distance of) building 102, or a sensor that isremote to the building 102. The sensors 131, 132 may include, forexample, temperature sensors, humidity sensors, occupancy sensors orsubstantially any other type of sensor as may be suitable for use in thesystem, for example, depending on the application (e.g., energy usagemonitoring). Other sensors might include mass or fluid flow sensorsassociated with an industrial process, proximity sensors for materialhandling or any other sensor that indicates activity in an energyconsuming process. In embodiments, any number (and type) of sensors maybe used in connection with the building signature system.

In embodiments, sensor 131 may, for example, correspond to a temperaturesensor configured to measure indoor air temperature at building 102.Additionally, in embodiments sensor 132 may, for example, correspond toa temperature sensor configured to measure outdoor air temperature atbuilding 102.

In the example embodiment shown, the BSIEDs 111, 112, 113, 114 are eachcoupled to respective building equipment (121, 122, 123, 124) in thebuildings 101, 102 in which the BSIEDs 111, 112, 113, 114 are installed.The building equipment 121, 122, 123, 124 may include, for example,machinery associated with a particular application (e.g., an industrialapplication) associated with the buildings 101, 102.

In embodiments, the BSIEDs 111, 112, 113, 114 may monitor and, in someembodiments, analyze building signature parameters associated with thebuilding equipment 121, 122, 123, 124 to which they are coupled. TheBSIEDs 111, 112, 113, 114 may also be embedded within the buildingequipment 121, 122, 123, 124 in some embodiments. According to variousaspects, one or more of the BSIEDs 111, 112, 113, 114 may be configuredto monitor utility feeds, including surge protectors, trip units, andtransformers, which are some examples of building equipment 121, 122,123, 124, and the BSIEDs 111, 112, 113, 114 can detect ground faults,voltage sags, voltage swells, momentary interruptions and oscillatorytransients, as well as fan failure, temperature, and harmonicdistortions, which are some example building signature parametersassociated with the equipment. The BSIEDs 111, 112, 113, 114 may alsomonitor devices, such as generators, including outputs, protectiverelays, battery chargers, and sensors (for example, water, and fuelsensors). According to another aspect, the BSIEDs 111, 112, 113, 114 candetect generator conditions including reverse power, temperature,overvoltage and undervoltage conditions, as well as other parameterssuch as temperature, including ambient temperature. A wide variety ofother monitoring and/or control functions can be performed by the BSIEDs111, 112, 113, 114, and the aspects and embodiments disclosed herein arenot limited to BSIEDs operating according to the above-mentionedexamples.

As shown in FIG. 1, the BSIEDs 111, 112, 113, 114 and sensors 131, 132are communicatively coupled to a central processing unit 140 via the“cloud” 150. In some embodiments, the BSIEDs 111, 112, 113, 114 andsensors 131, 132 may be directly communicatively coupled to the cloud150, as BSIED 111 is in the illustrated embodiment. In otherembodiments, the BSIEDs 111, 112, 113, 114 and sensors 131, 132 may beindirectly communicatively coupled to the cloud 150, for example,through an intermediate device, such as a cloud-connected hub 150, asBSIEDs 112, 113, 114 are in the illustrated embodiment. Thecloud-connected hub 150 may, for example, provide the BSIEDs 112, 113,114 with access to the cloud 150, the central processing unit 140 andother portions of the building signature system (e.g., sensors 121, 122,as will be discussed).

As used herein, the terms “cloud” and “cloud computing” are intended torefer to computing resources connected to the Internet or otherwiseaccessible to BSIEDs 111, 112, 113, 114 via a communication network,which may be a wired or wireless network, or a combination of both. Thecomputing resources comprising the cloud 150 may be centralized in asingle location, distributed throughout multiple locations, or acombination of both. A cloud computing system may divide computing tasksamongst multiple racks, blades, processors, cores, controllers, nodes orother computational units in accordance with a particular cloud systemarchitecture or programming. Similarly, a cloud computing system maystore instructions and computational information in a centralized memoryor storage, or may distribute such information amongst multiple storageor memory components. The cloud system may store multiple copies ofinstructions and computational information in redundant storage units,such as a RAID array.

The central processing unit 140 may be an example of a cloud computingsystem, or cloud-connected computing system. In embodiments, the centralprocessing unit 140 may be a server located within the buildings 101,102 in which the BSIEDs 111, 112, 113, 114 are installed, or may beremotely-located cloud-based service. The central processing unit 140may include computing functional components similar to those of theBSIEDs 111, 112, 113, 114 is some embodiments, but may generally possessgreater numbers and/or more powerful versions of components involved indata processing, such as processors, memory, storage, interconnectionmechanisms, etc. The central processing unit 140 can be configured toimplement a variety of analysis techniques to identify patterns inreceived measurement data from the BSIEDs 111, 112, 113, 114, asdiscussed further below. The various analysis techniques discussedherein further involve the execution of one or more software functions,algorithms, instructions, applications, and parameters, which are storedon one or more sources of memory communicatively coupled to the centralprocessing unit 140. In certain embodiments, the terms “function”,“algorithm”, “instruction”, “application”, or “parameter” may also referto a hierarchy of functions, algorithms, instructions, applications, orparameters, respectively, operating in tandem. A hierarchy may comprisea tree-based hierarchy, such a binary tree, a tree having one or morechild nodes descending from each parent node, or combinations thereof,wherein each node represents a specific function, algorithm,instruction, application, or parameter.

In addition, as also discussed in more detail below, the centralprocessing unit 140 can be configured to generate updates ormodifications to the building signature operational models of any of theBSIEDs 111, 112, 113, 114 and to provide the revised (or new)operational model(s) to the BSIED(s). Cloud-connectivity of the centralprocessing unit 140 provides the ability to have one central processingunit 140 (or a coordinated group of central processing units) provideupdated building signature operational models to multiple BSIEDs 111,112, 113, 114 deployed at different physical locations (here, buildings101, 102). In embodiments, since the central processing unit 140 isconnected to the cloud 150, it may access additional cloud-connecteddevices or databases 190 via the cloud 150. For example, the centralprocessing unit 140 may access the Internet and receive information suchas weather data, utility pricing data, or other data that may be usefulin analyzing the measurement data received from the BSIEDs 111, 112,113, 114 and/or in reprogramming the building signature operationalmodels of any of the BSIEDs 111, 112, 113, 114, as discussed furtherbelow.

In embodiments, the cloud-connected devices or databases 190 maycorrespond to a device or database associated with one or more externaldata sources. In embodiments, the external data sources may includeweather data sources. For example, in embodiments the central processingunit 140 may be coupled to receive weather data (e.g., historicalrainfall and temperature data) from the United States National WeatherService or another weather data source, and be configured to use thereceived weather data in generating a new or updated BSOM for the BSIEDs111, 112, 113, 114, as will be discussed further in connection withfigures below.

Additionally, in embodiments the cloud-connected devices or databases190 may correspond to a user device from which a user may provide userinput data. In embodiments, a user may view information about the BSIEDs111, 112, 113, 114 (e.g., BSIED makes, models, types, etc.) and datacollected by the BSIEDs 111, 112, 113, 114 (e.g., energy usagestatistics) using the user device. Additionally, in embodiments the usermay configure the BSIEDs 111, 112, 113, 114 using the user device. Forexample, the user may submit additional parameters to be considered ingenerating a new or updated BSOM for the BSIEDs 111, 112, 113, 114, aswill be discussed further in connection with figures below.

The central processing unit 140 may also be coupled to one or moresensor devices (e.g., 131, 132) and configure to receive sensor datafrom the sensor devices in generating the a new or updated BSOM for theBSIEDs 111, 112, 113, 114. Systems and methods of generating new BSOMsare discussed further below.

As also shown in FIG. 1, one or more of the BSIEDs 111, 112, 113, 114may further be communicatively coupled to one or more peripheral or“downstream” devices 170, 180. For example, a BSIED 111 may providecontrol signals to the downstream devices 170, 180 based on themeasurement data collected by the BSIED 111 or other information orinstructions received from the central processing unit 140. In certainexamples, BSIED 111 may be capable of bidirectional communication with adownstream device 170 such as another BSIED or other programmable devicecapable of transmitting and receiving data. In certain examples BSIED111 may also be capable of unidirectional transmission to certain otherdownstream devices 180.

In certain examples at least one of the downstream devices 170, 180 maybe configured to measure same or similar parameters as BSIED 111, forexample. However, in certain examples the at least one of the downstreamdevices 170, 180 may not have the capability to interface with the cloud150, but may have ability to interface with the BSIED 111. In suchexamples, the BSIED 111 may act as a “gateway” or “communication proxy”for such downstream devices 170, 180.

In embodiments, by leveraging the cloud-connectivity and enhancedcomputing resources of the central processing unit 140 relative to theBSIEDs 111, 112, 113, 114, sophisticated analysis can be performed onthe BSOD retrieved from one or more BSIEDs, as well as on the additionalsources of data discussed above, when appropriate. This analysis can beused to dynamically reprogram BSIEDs (e.g., generate new BSOMsassociated with the BSIEDs) responsive to changing or ongoing conditionsrevealed by the analysis, as will be discussed further in connectionwith figures below.

Referring to FIG. 2, an example BSIED 200 that may be suitable for usein a building signature system, such as the building signature systemshown in FIG. 1, for example, includes a controller 210, a memory device215, storage 225, and an interface 230. The BSIED 200 also includes aninput-output (I/O) port 235, a sensor 240, a communication module 245,and an interconnection mechanism 220 for communicatively coupling two ormore BSIED components 210-245.

The memory device 215 may include volatile memory, such as DRAM or SRAM,for example. The memory device 215 may store storing programs and datacollected during operation of the BSIED 200. For example, in embodimentsin which the BSIED 200 is configured to monitor or measure one or morebuilding signature parameters associated with building equipment (e.g.,121, shown in FIG. 1) in a building signature system, the memory device215 may store the monitored building signature parameters. Additionally,the BSOM(s) associated with the BSIED 200, or portions of the BSOM(s),may be stored in the memory device 215 in some embodiments.

The storage system 225 may include a computer readable and writeablenonvolatile recording medium, such as a disk or flash memory, in whichsignals are stored that define a program to be executed by thecontroller 210 or information to be processed by the program. The mediummay include, for example, a disk or flash memory. The controller 210 maycontrol transfer of data between the storage system 225 and the memorydevice 215 in accordance with known computing and data transfermechanisms. In embodiments, the building signature parameters monitoredor measured by the BSIED 200, and/or the BSOM(s) associated with theBSIED 200 (or portions of the BSOM(s)), may be stored in the storagesystem 225.

The I/O port 235 can be used to couple building equipment (e.g., 121,shown in FIG. 1) to the BSIED 200, and the sensor 240 can be used tomonitor or measure the building signature parameters associated with thebuilding equipment 200. The I/O port 235 can also be used to coupledexternal devices, such as sensor devices (e.g., 131, shown in FIG. 1)and/or user input devices (e.g., local or remote computing devices) (notshown), to the BSIED 200. The I/O port 235 may further be coupled to oneor more user input/output mechanisms, such as buttons, displays,acoustic devices, etc., to provide alerts (e.g., to display a visualalert, such as text and/or a steady or flashing light, or to provide anaudio alert, such as a beep or prolonged sound) and/or to allow userinteraction with the BSIED 200.

The communication module 245 may be configured to couple the BSIED 200to one or more external communication networks or devices. Thesenetworks may be private networks within a building in which the BSIED200 is installed, or public networks, such as the Internet. Inembodiments, the communication module 245 may also be configured tocouple the BSIED 200 to a cloud-connected hub (e.g., 150, shown in FIG.1), or to a cloud-connected central processing unit (e.g., 140, shown inFIG. 1), associated with a building signature system including BSIED200. The cloud-connected central processing unit may be coupled, forexample, to receive building signature operational data (BSOD) generatedby a BSIED (e.g., 200), and be configured to generate a new or updatedBSOM associated the BSIED, for example, based on the BSOD and additionalexternal data received from other sources.

The BSIED controller 210 may include one or more processors that areconfigured to execute the BSOM(s) associated with the BSIED 200 toperform the specified function(s) of the device. The processor(s) can bea commercially available processor, such as the well-known Pentium™,Core™, or Atom™ class processors available from the Intel Corporation.Many other processors are available, including programmable logiccontrollers. The controller 210 can execute an operating system todefine a computing platform on which the application(s) included in theBSOM(s) of the BSIED can run.

In embodiments, the building signature parameters monitored or measuredby the BSIED 200 may be received at an input of the controller 210 asbuilding signature input data (BSID), and the controller 210 may processthe BSID using the BSOM(s) associated with the BSIED 200 to generatebuilding signature operational data (BSOD) at an output thereof. Inembodiments, the BSOD may correspond to an output of the BSIED 200. TheBSOD may be provided at I/O port(s) 235, for example. In embodiments,the BSOD may be received by a cloud-connected central processing unit,for example, for further processing (e.g., to generate new or updatedBSOM(s), as briefly discussed above), and/or by building equipment towhich the BSIED is coupled (e.g., for controlling one or more parametersassociated with the equipment, as will be discussed further below).

Components of the BSIED 200 may be coupled together by theinterconnection mechanism 220, which may include one or more busses,wiring, or other electrical connection apparatus. The interconnectionmechanism 220 may enable communications (e.g., data, instructions, etc.)to be exchanged between system components of the BSIED 200.

It is understood that BSIED 200 is but one of many potentialconfigurations of BSIEDs in accordance with various aspects of thedisclosure. For example, BSIEDs in accordance with embodiments of thedisclosure may include more (or fewer) components than BSIED 200.Additionally, in embodiments one or more components of BSIED 200 may becombined. For example, in embodiments memory 215 and storage 225 may becombined.

Referring to FIG. 3, an example building 300 associated with a buildingsignature system in accordance with embodiments of the disclosure isshown having a plurality of BSIEDs 310, 315, 320, 325, 330 installedtherein. In embodiments, the BSIEDs 310, 315, 320, 325, 330 may takevarious forms and be configured to measure or monitor a variety ofbuilding signature parameters. For example, BSIEDs 310, 315, 320 maycorrespond to a first type of BSIED configured to monitor first buildingsignature parameters associated with a first type of building equipment(e.g., 121, shown in FIG. 1) installed in the building 300.Additionally, BSIED 325 may correspond to a second type of BSIEDconfigured to monitor second building signature parameters associatedwith a second type of building equipment installed in the building 300.Further, BSIED 330 may correspond to a third type of BSIED configured tomonitor third building signature parameters associated with a third typeof building equipment installed in the building 300.

In embodiments, at least one of the first, second and third BSIED typesincludes an energy meter, a power quality monitor, a waveform monitor, aprogrammable sensing device, an uninterruptible power supply, a powerquality correction device, and/or a harmonic filter with meteringcapabilities. Additionally, in embodiments at least one of the first,second and third BSIED types includes an occupancy IED or a weatherstation IED. Further, in embodiments at least one of the first, secondand third BSIED types includes a programmable logic controller (PLC),for example, associated with building equipment (e.g., in building 300).The PLC may, for example, accumulate operational data associated withthe building equipment. As one example, the operational data associatedwith the building equipment may correspond to product output (e.g.,number of items produced, such as shoes) by the building equipment.

In embodiments, the building signature operational data generated by atleast one of the first, second and third BSIEDs may be used to generatea building signature operational model associated with other ones of thefirst, second and third BSIEDs. For example, in embodiments in which thefirst BSIED includes an occupancy IED and the second BSIED includes aPLC associated with building equipment, building signature output datagenerated by the first BSIED may be used to generate a buildingsignature operational model associated with the second BSIED, forexample, to map intensity of equipment output (e.g., as measured by thesecond BSIED) versus building occupancy (e.g., as measured by the firstBSIED).

In embodiments, at least one of the first, second and third buildingsignature parameters monitored by the first, second and third BSIEDtypes includes energy consumption parameters (e.g., voltage, current,power, etc.) associated with the respective building equipment (i.e.,first, second, third building equipment).

The BSIEDs 310, 315, 320, 325, 330 shown in FIG. 3 may each have anassociated complexity (or set of functional capabilities). For example,BSIED 320 may correspond to a “basic” BSIED, BSIED 315 may correspond toan “intermediate” BSIED, and BSIED 310 may correspond to an “advanced”BSIED. In embodiments, intermediate BSIED 315 may have morefunctionality (e.g., energy measurement capabilities) than basic BSIED320, and advanced BSIED 310 may have more functionality thanintermediate BSIED 315. For example, in embodiments basic BSIED 320 maybe capable of measuring instantaneous voltage, current and power, andadvanced BSIED 310 may be capable of measuring instantaneous and averagemaximum voltage, current, power, frequency, power factor, demand andenergy.

In embodiments, intermediate BSIED 315 may also be responsive to morebuilding signature data sources (and building signature input dataassociated with the building signature data sources) than basic BSIED320. Additionally, in embodiments advanced BSIED 310 may be responsiveto more building signature data sources (and building signature inputdata associated with the building signature data sources) thanintermediate BSIED 315.

As illustrated, each of the BSIEDs 310, 315, 320, 325, 330 has anassociated BSOM (here, BSOMs 311, 316, 321, 326, 330). The BSIEDs 310,315, 320, 325, 330 may be responsive to respective building signatureinput data to generate building signature operational data using theBSOMs 311, 316, 321, 326, 330. In embodiments, the BSOMs 311, 316, 321,326, 330 are device and site (e.g., building 300) specific. Moreparticularly, in embodiments the BSOMs 311, 316, 321, 326, 330 may begenerated specifically for the BSIEDs 310, 315, 320, 325, 330 to whichthe BSOMs 311, 316, 321, 326, 330 are associated, and the building 300in which the BSIEDs 310, 315, 320, 325, 330 are installed. Additionalaspects of BSOMs and BSIEDs (including evaluation, generation andselection of BSOMs for BSIEDs) are described further below in connectionwith figures below.

Referring to FIGS. 4-9, several flowcharts (or flow diagrams) are shown.Rectangular elements (typified by element 405 in FIG. 4), as may bereferred to herein as “processing blocks,” may represent computersoftware instructions or groups of instructions. Diamond shaped elements(typified by element 410 in FIG. 4), as may be referred to herein as“decision blocks,” represent computer software instructions, or groupsof instructions, which affect the execution of the computer softwareinstructions represented by the processing blocks. The processing blocksand decision blocks can represent steps performed by functionallyequivalent circuits such as a digital signal processor circuit or anapplication specific integrated circuit (ASIC).

The flowcharts do not depict the syntax of any particular programminglanguage. Rather, the flowcharts illustrate the functional informationone of ordinary skill in the art requires to fabricate circuits or togenerate computer software to perform the processing required of theparticular apparatus. It should be noted that many routine programelements, such as initialization of loops and variables and the use oftemporary variables are not shown. It will be appreciated by those ofordinary skill in the art that unless otherwise indicated herein, theparticular sequence of blocks described is illustrative only and can bevaried. Thus, unless otherwise stated, the blocks described below areunordered; meaning that, when possible, the blocks can be performed inany convenient or desirable order including that sequential blocks canbe performed simultaneously and vice versa.

Referring to FIG. 4, a flowchart illustrates an example method 400 formanaging (e.g., monitoring and/or updating) a BSIED (e.g., 111, shown inFIG. 1) that can be implemented, for example, on a cloud-connectedcentral processing unit (e.g., 140, shown in FIG. 1). The BSIED may be aBSIED of a building signature system including one or more BSIEDs, andthe cloud-connected central processing unit may be communicativelycoupled to the BSIED (e.g., through cloud 150, shown in FIG. 1).

As illustrated in FIG. 4, the method 400 begins at block 405, where thecloud-connected central processing unit processes building signatureoperational data (BSOD) received from the BSIED to identify the BSIEDfrom which the BSOD was received from. An example method for identifyingthe BSIED is discussed below in connection with FIG. 5. However, howeverlet it suffice here to say that the cloud-connected central processingunit (CCCPU) may identify the BSIED by analyzing the BSOD foridentifying information associated with BSIED. The identifyinginformation may, for example, be encoded in the BSOD.

At block 410, the CCCPU processes the BSOD to determine if a buildingsignature operational model (BSOM) associated with the BSIED, and usedby the BSIED to generate the BSOD, needs to be updated. Example methodsof determining if a BSOM needs to be updated are discussed below inconnection with FIGS. 6 and 7. However, however let it suffice here tosay that the CCCPU may determine if the BSOM needs to be updated byevaluating if any changes have been made to the BSIED or buildingsignature system including the BSIED, and/or by evaluating the accuracyof the BSOD (or BSOM). In embodiments, the CCCPU may determine if theBSOM needs to be updated by evaluating if a new BSOM exists for theBSIED. As discussed in figures above, a BSIED may have one or moreassociated BSOMs.

If the CCCPU determines that the BSOM needs to be updated, the methodproceeds to a block 415. Alternatively, if the CCCPU determines that theBSOM does not need to be updated, the method may end. In embodiments,subsequent to the method ending, the CCCPU may transmit a message (orother indication) to the BSIED indicating that the BSOM does not need tobe updated. In embodiments, the method may be initiated againautomatically (e.g., after a predetermined time period) or in responseto the CCCPU receiving a control signal from a control source (e.g., auser input device), for example, requesting that BSOM(s) associated withthe BSIED be evaluated.

At block 415, in response to determining that the BSOM needs to beupdated, the CCCPU selects a new BSOM for the BSIED. In embodiments, thenew BSOM is selected from a BSOM library, for example, stored on amemory device associated with the CCCPU. The memory device may contain aplurality of BSOMs. In embodiments, each of the plurality of BSOMs iscustom tailored for a particular BSIED, and is site specific (e.g.,specific to a building in which the BSIED is installed). The pluralityof BSOMs may be generated by the CCCPU, for example, in response toreceiving BSOD and input data from one or more respective data sourcesassociated with the BSIEDs for which the plurality of BSOMs areintended. In embodiments, the data sources include at least one of atemperature sensor, a humidity sensor, and an occupancy sensorconfigured to generate respective temperature, humidity and occupancyinput data pertaining to the environment(s) in which the BSIEDs areinstalled.

In embodiments, the new BSOM for the BSIED is selected based, at leastin part, on one or more characteristics associated with the BSIED. Thecharacteristics associated with the BSIED may include, for example,BSIED type, BSIED complexity, and building signature parametersmonitored by the BSIED. A BSIED of a first type that is responsive to afirst type of building signature input data (BSID) may, for example,require a different BSOM than a BSIED of a second type that isresponsive to a second type of BSID that is different from the firsttype of BSID. Additional aspects of selecting a BSOM for a BSIED (andgenerating a BSOM) are described below in connection with FIG. 8, forexample.

At block 420, the new BSOM is transmitted to the BSIED (e.g., via thecloud 150) for installation on the BSIED. Additionally, at block 425,which is optional in some embodiments, a validation procedure may beused to confirm that the BSOM was correctly transmitted by the CCCPU tothe BSIED. For example, a checksum or similar method may be used (on theBSIED and/or CCCPU) to confirm that the BSOM was received by the BSIEDintact and unaltered.

In embodiments, operation of the new BSOM may also be validated prior totransmission to the BSIED to confirm that the new BSOM operates asexpected. For example, BSID may be processed on the CCCPU using the newBSOM to generate BSOD associated with the new BSOM. Additionally,accuracy of the BSOD may be validated, for example, by comparing theBSOD (i.e., new BSOD) to historical BSOD.

In some embodiments, the BSID may be received from one or more buildingsignature data sources (BSDSs) at an input of the BSIED, and be madeavailable to the CCCPU via the cloud. In embodiments, the BSDSs mayinclude equipment to which the BSIED is coupled, and the BSID mayinclude energy usage information associated with the BSDSs.Additionally, in embodiments the BSID may correspond to test BSID (e.g.,specifically for validating BSOMs), and the test BSID may be retrievedfrom a memory device of the BSIED.

Subsequently to block 425, the method 400 may end. In embodiments, themethod 400 ending may be indicative of a new BSOM having beensuccessfully installed on the BSIED. In embodiments, once the new BSOMis successfully installed on the BSIED, the BSIED may disconnect fromthe cloud and operate independently from the cloud. This is an advantagebecause it allows intentional disconnection (for security reasons, forexample) and also to provide protection against unintentionaldisconnection, as would result from a communications interruption withthe cloud.

Referring to FIG. 5, a flowchart illustrates an example method 500 foridentifying a BSIED. The method 500 may be implemented, for example, ona CCCPU that is communicatively coupled to the BSIED. In embodiments,the method 500 may correspond to example steps performed at block 405 ofmethod 400 discussed above in connection with FIG. 4.

As illustrated in FIG. 5, the method 500 begins at block 505, where theCCCPU determines if a predetermined time period has elapsed, or anotherpredetermined condition has occurred, since a BSOM associated with theBSIED has last been updated or verified. As discussed in figures above,a BSIED may have one or more associated BSOMs.

In embodiments, the CCCPU may determine if the predetermined time periodhas elapsed, or another predetermined condition has occurred, bycomparing the version number, update history, etc. of the BSOM with theversion number, update history, etc. of the latest version of the BSOM.The CCCPU may, for example, store version numbers, update histories,etc. of BSOM(s) currently on the BSIED, as well as version numbers,update histories, etc. of a number of BSOM(s) that may be suitable forthe BSIED, and other BSIEDs, on a memory device associated with theCCCPU. Recomputation (or regeneration) of a BSOM might be triggered, forexample, by an improvement in the algorithms used to generate the BSOMfrom the BSID and BSOD.

In embodiments, the predetermined time period is associated with theBSIED (or the BSOM associated with the BSIED). For example, a BSIEDcomprising a BSOM which requires frequent updates, for example, due tochanging environmental (e.g., temperature and humidity) conditions, mayhave a predetermined time period that is less than the predeterminedtime period for a BSIED comprising a BSOM which requires less frequentupdates. Additionally, in embodiments the predetermined time period isassociated with a group of BSIEDs. The group of IEDs may comprise sameor similar types of BSIEDs in some embodiments, and different types ofBSIEDs in other embodiments. For example, the group of BSIEDs maycomprise a plurality of BSIEDs associated with a particular building orgeographic location. The predetermined time period may correspond to aday, a week, a month, or substantially any other time period as may besuitable for the BSIED and/or application(s) associated with the BSIED.In embodiments, the BSOM is a model that captures at least how thebuilding in which the BSIED is installed reacts to changes in weather(and other conditions) under substantially any circumstance. As such,rapidly varying weather, for example, may not require frequent changesto the model since the model is designed to handle that. However, inembodiments in which the building changes frequently in its controlsystem or construction, for example, then the BSOM may need to beupdated (sometimes frequently) in response to the changes.

If the CCCPU determines that the predetermined time period has elapsed,or another predetermined condition has occurred since BSOM associatedwith the BSIED has last been updated or verified, the method proceeds toa block 510. Alternatively, if the CCCPU determines that thepredetermined time period has not elapsed, or another predeterminedcondition has not occurred since the BSOM has last been updated orverified, the method may return to block 5105 and repeat again in someembodiments. In other embodiments, the method may end and be initiatedagain, for example, in response to the CCCPU receiving a control signalfrom a control source (e.g., a user input device).

At block 510, the CCCPU requests BSOD from the BSIED. For example, theCCCPU may send a data request signal or packet to the BSIED (e.g., viathe cloud) to request BSOD from the BSIED. At block 515, in response toreceiving the data request signal or packet, the BSIED may transmit BSODto the CCCPU (e.g., via the cloud). In embodiments, the BSOD correspondsto (or is indicative of) one or more building signature parameters(e.g., energy usage parameters) monitored or sensed by the BSIED.Additionally, in embodiments the BSOD may contain identifyinginformation associated with the BSIED. For example, at least a portionof the BSOD may include identifying information associated with theBSIED embedded therein. Additionally or alternatively, prior to, after,or during transmission of the BSOD, the BSIED may transmit identifyinginformation associated with the BSIED to the CCCPU. The identifyinginformation may include, for example, a serial number associated withthe BSIED. The serial number associated with the BSIED may be used, forexample, to identify the building in which the BSIED is installed, theapplication(s) in which the BSIED is being used, customer associatedwith the BSIED, etc. In embodiments, the identification may occur usingcommercial tracking software, for example.

At block 520, the CCCPU may identify the BSIED based on the BSOD (and/orother information) received from the BSIED at block 515. Subsequent toblock 520, the method 500 may end. In embodiments, the method ending maybe indicative of the CCCPU having identified a BSIED from which BSOD isreceived from, and the CCCPU being ready to determine if a BSOMassociated with the BSIED needs to be updated (e.g., at block 410 ofmethod 400).

Referring to FIG. 6, a flowchart illustrates an example method 600 fordetermining if a BSOM associated with a BSIED needs to be updated. Inembodiments, the method 600 may correspond to example steps performed atblock 410 of method 400 discussed above in connection with FIG. 4.

As illustrated in FIG. 6, the method 600 begins at block 605, where theCCCPU determines if any changes (e.g., software and/or hardware changes)have been made to a BSIED or a building signature system which mayinclude the BSIED.

In embodiments, the CCCPU may examine BSOD, alone or in combination withother types of data, received from the BSIED (e.g., at block 515 ofmethod 500) or other sources, to determine if any changes have been madeto the BSIED or building signature system. For example, in embodimentsthe BSOD received from the BSIED may contain information indicating anumber of devices (e.g., BSIED or otherwise) in the building signaturesystem, and the CCCPU may use this information to determine if anychanges have been made to the system. Additionally, in embodiments theBSOD may contain device specific information (e.g., hardware and/orsoftware information) associated with the BSIED from which the BSOD wasreceived (and/or of other devices in the building signature system), andthe CCCPU may use this information to determine if any changes have beenmade to the BSIED (or the system).

In embodiments, the CCCPU may also monitor the building signature system(e.g., by examining data received from one or more sensors) to determineif any changes have been made to the system. For example, the CCCPU maymonitor the system to determine if a new device has been added to (orremoved from) the system. Additionally, the CCCPU may be coupled a userinput device and configured to receive user input indicating that a newdevice has been added to (or removed from) the system. For example, ahuman operator might initiate a request for generation or calculation ofa new BSOM based on a known change (or changes) in the building that isnot evident to the CCCPU. If, for example, light bulbs in the buildingwere replaced with more efficient light bulbs on a particular date, thena human initiated request might be sent to the CCCPU to request a newBSOM be created to characterize the post-upgrade behavior.

If the CCCPU determines that a change has been made to the buildingsignature system or BSIED (e.g., in response to monitoring by the CCCPUor user input), the method 600 proceeds to a block 610. Alternatively,if the CCCPU determines that no changes have been made to the buildingsignature system or BSIED (e.g., in response to monitoring by the CCCPUor user input), the method 600 may end. The method 600 ending may, forexample, be indicative of a new or updated operational model not beingneeded in response to changes in the building signature system or BSIEDsince no changes to the building signature system or BSIED weredetected.

At block 610, the CCCPU determines the particular change(s) in thebuilding signature system or BSIED (i.e., at block 605, the CCCPUdetects if there are any changes, and at block 610, the CCCPU identifiesthe changes). In embodiments, the CCCPU determines the change(s) in thebuilding signature system or BSIED by examining at least one of: theBSOD received from the BSIED, data received from one or more other datasources (e.g., sensors) in the building signature system, and user inputdata. For example, in embodiments in which the BSIED receives a hardwareor firmware update, the BSIED may encode a message in BSOD indicatingthe update to the BSIED, and the CCCPU may examine the message in theBSOD to determine the change(s) in the BSIED. As another example, inembodiments in which a new BSIED has been added to the buildingsignature system, the new BSIED (or a sensor communicatively coupled tothe system) may transmit a message to the CCCPU indicating that the newBSIED has been added to the system. As a further example, in embodimentsin which a new BSIED has been added to the system, a user may provide anindication that the new BSIED has been added to the system using a userinput device coupled to the CCCPU.

At block 615, the CCCPU determines the BSOM associated with the BSIEDneeds to be updated in response to the detected change(s) in thebuilding signature system or the BSIED. For example, in embodiments inwhich the BSIED receives a hardware or firmware update, the CCCPU maydetermine that the BSIED requires a new or updated BSOM. Additionally,in embodiments in which a new BSIED is added to the building signaturesystem, the CCCPU may determine that the BSIED requires a new or updatedBSOM.

If the CCCPU determines that the BSOM associated with the BSIED needs tobe updated in response to the detected change(s), the method 600 may endand the CCCPU may proceed to select a new BSOM for the BSIED (e.g., atblock 415 of method 400). Alternatively, if the CCCPU determines thatthe BSOM does not need to be updated in response to the detectedchange(s), the method 600 may end and the CCCPU may proceed to informthe BSIED that the BSOM does not need to be updated (e.g., due to theBSIED having the latest BSOM for the BSIED).

Referring to FIG. 7, a flowchart illustrates another example method 700for determining if a BSOM associated with a BSIED needs to be updated.Similar to method 600, in embodiments method 700 may correspond toexample steps performed at block 410 of method 400 discussed above inconnection with FIG. 4. In embodiments, method 700 may be performedalone or in combination with method 600 (and other methods) to determineif the BSOM needs to be updated.

As illustrated in FIG. 7, the method 700 begins at block 705 where theCCCPU compares BSOD retrieved from a BSIED (e.g., at block 405 of method400) with historical BSOD associated with the BSIED. In embodiments, thehistorical BSOD may be stored on a memory device associated with theCCCPU.

At block 710, the CCCPU determines if the retrieved BSOD aligns with thehistorical BSOD. If the CCCPU determines that the retrieved BSOD alignswith the historical BSOD, the method 700 may end. The method 700 endingmay, for example, be indicative of the BSOM associated with the BSIEDnot needing to be updated since the retrieved BSOD aligns with thehistorical BSOD (i.e., the retrieved BSOD is determined to be accurate).Alternatively, if the CCCPU determines that the retrieved BSOD does notalign with the historical BSOD (i.e., the retrieved BSOD is determinedto be inaccurate), the method proceeds to a block 715.

Taking the BSOD to be the quantity predicted by the BSOM (buildingenergy consumption being the most common example), accuracy of the BSOMmay be assessed by the ‘CUSUM of residuals’ method, for example, where arunning sum of the difference between the model output and the measuredenergy consumption is evaluated over a period of months or more. If themeasured values of energy consumption have a sustained difference fromthe model's prediction, for example, it may be time to update the model.A rule like “if the predicted energy consumption for a three monthperiod differs from the actual consumption by more than 10%, recomputethe model” would be an example. Other example methods that may be usedto assess accuracy of the BSOM are described in co-pending U.S.Published Application No. 2013/0151179 entitled “Automated MonitoringFor Changes in Energy Consumption Parameters,” which is assigned to theassignee of the present disclosure and incorporated herein by referencein its entirety.

At block 715, the CCCPU determines the reason(s) for the detecteddeviation between the retrieved BSOD and the historical BSOD. Forexample, the CCCPU may analyze temperature information to determine ifthe BSIED from which the BSOD was retrieved has been subject tounusually high or low temperatures (e.g., due to an exceptionally longwinter season). In embodiments, current temperature information may bereceived from one or more temperature sensors (e.g., 131, shown inFIG. 1) proximate to the BSIED. Additionally, in embodiments historicaltemperature information may be stored in a memory device associated withthe CCCPU, and/or received from one or more external data sources (e.g.,191, shown in FIG. 1). The external data sources may include, forexample, the United States National Weather Service.

In embodiments, the CCCPU may also analyze occupancy information todetermine if occupancy of a building in which the BSIED is installed hassignificantly increased or decreased, for example, due to an increasedor decreased demand for production at the building. In embodiments,current occupancy information may be received from one or more occupancysensors (e.g., 131, shown in FIG. 1) proximate to the BSIED.Additionally, in embodiments historical occupancy information may bestored in a memory device associated with the CCCPU.

At block 720, the CCCPU determines if updating a BSOM associated withthe BSIED will likely decrease the detected deviation (e.g., due to thecurrent BSOM being inaccurate, or not the latest BSOM for the BSIED). Asdiscussed above, the BSOM associated with the BSIED is used to generatethe BSOD received by the CCCPU.

If the CCCPU determines that updating the BSOM will likely decrease thedetected deviation, the method 700 proceeds to a block 725 where it isdetermined that a new BSOM is need for the BSIED. Alternatively, if theCCCPU determines that updating the operational model will likely notdecrease detected deviation (e.g., due to the BSIED already having thelatest BSOM for the BSIED), the method 700 proceeds to a block 730 whereit is determined that a new BSOM is not needed for the BSIED. Afterblocks 725 and 730, the method 700 may end. The method ending may, forexample, be indicative of the detected deviation not being due to thecurrent operational model being outdated or inaccurate. For example, thedetected deviation may be due to a hardware issue with the BSIED (whichmay require repair by a technician).

Referring to FIG. 8, a flowchart illustrates an example method 800 forselecting a new BSOM for a BSIED, for example, in response to the CCCPUdetermining that a new BSOM is need for the BSIED. In embodiments, themethod 800 may correspond to example steps performed at block 415 ofmethod 400 discussed above in connection with FIG. 4.

As illustrated in FIG. 8, the method 800 begins at block 805, where theCCCPU determines a proposed BSOM for the BSIED. In embodiments, theproposed BSOM is selected from a plurality of BSOMs stored on a memorydevice associated with the CCCPU. The memory device may contain aplurality of BSOMs (e.g., in a BSOM library). In embodiments, theproposed BSOM is selected from the plurality of BSOMs based on the BSIEDtype, and particular configuration of the BSIED. For example, a BSIEDresponsive to a first set of building signature inputs may require adifferent BSOM from a BSIED responsive to a second set of buildingsignature inputs that is different from the first set of buildingsignature inputs.

As briefly discussed above in connection with FIG. 4, in embodiments theplurality of BSOMs may be generated by the CCCPU in response toreceiving BSOD and input data from one or more respective data sourcesassociated with the BSIEDs for which the plurality of BSOMs areintended. For example, a BSIED corresponding to an electrical meterconfigured to monitor energy consumption of a building in which theBSIED is installed, may have a BSOM (e.g., a custom BSOM) generated inresponse to BSOD (e.g., meter data) received from the BSIED and otherdriver data associated with a building in which the BSIED is installed.In embodiments, the driver data may correspond to temperature data(e.g., average temperature), wind data (e.g., wind speed), productiondata (e.g., production units), and occupancy data. In embodiments, theBSOM can be generated in response to the BSOD and other driver data, andby examining historical performance of a building's consumption againsthistorical environmental data, using a variety of techniques including,for example, the ASHRAE 14-2002 standard for energy modeling.

In embodiments, the techniques used to create the BSOMs may be updatedfrom time to time as “better” (e.g., more accurate) methods aredeveloped. Due to the BSOMs being created in the cloud, the BSOMs may bemore amenable to frequent updates.

Additionally, in embodiments the BSOM may be periodically adjusted ortuned, for example, in response to user input. For example, a user on auser device communicatively coupled to the CCCPU may transmit user inputdata to the CCCPU and the CCCPU may adjust or tune the operational modelin response to the user input data. The BSOM may be tuned, for example,using user input data containing information that is not already encodedin the BSOD that the CCCPU uses to generate the operational model.Additionally, BSOD that is known to be invalid (or otherwiseinaccurate), for example, due to a plant maintenance shutdown, can beremoved from the BSOD in response to the user input.

At block 810, the CCCPU determines if the BSIED supports the proposedBSOM. In embodiments, the CCCPU determines if the BSIED supports theproposed BSOM by evaluating one or more parameters (or characteristics)of the BSIED (e.g., make, model, etc. of the BSIED) with parameters(e.g., BSIED make, BSIED model, etc.) that the proposed BSOM supports.For example, a relatively simple BSIED may not support a BSOM intendedfor a more complex BSIED. The more complex BSIED may, for example, beresponsive to more building signature inputs than the relatively simpleBSIED, and be configured to generate more outputs (e.g., buildingsignature operational data) than the relatively simple BSIED. Asdiscussed in figures above, BSOMs according to embodiments of thedisclosure are custom tailored for a particular BSIED, and are sitespecific (e.g., specific to a building in which the BSIED is installed).

If the CCCPU determines that the BSIED supports the proposed BSOM, themethod proceeds to a block 815. Alternatively, if the CCCPU determinesthat the BSIED does not support the proposed operational BSOM, themethod proceeds to a block 835.

At block 815, the CCCPU determines if the current BSOM (i.e., the BSOMcurrently used by the BSIED) can be updated to the proposed BSOM. Forexample, in some embodiments one or more parameters can be added to,removed from, or modified in the current BSOM to update the current BSOMto the proposed BSOM. The foregoing may, for example, reduce (or ideallyeliminate) any downtime for the BSIED in updating the BSOM. For example,in embodiments in which parameters can be added to, removed from, ormodified in the current BSOM to update the current BSOM to the proposedBSOM, the CCCPU can generate the new or modified parameters, andtransmit them to the BSIED for updating without interrupting operationof the BSIED. This avoids any interruption in operation of the BSIEDthat might result from a more invasive update of the device's operation,and avoids the risk that might accompany a firmware update.

If the CCCPU determines that the current BSOM can be updated to theproposed BSOM, the method proceeds to a block 820. Alternatively, if theCCCPU determines that the current BSOM cannot be updated to the proposedBSOM (e.g., due to various operational model constraints), the proceedsto a block 825.

At block 820, the CCCPU generates the new or updated parameters for theBSOM, and/or generates a message indicating which parameters should beremoved from the current BSOM. Examples of parameters that may beupdated in a BSOM include, for example, regression coefficients ofdriver variables in an ASHRAE-2002 style regression model, or theschedule times of switching between models for a time-segmented model.In embodiments, the new or updated parameters of the BSOM may generated(or adjusted or tuned) in response to user input (e.g., from an “expert”user through a user device). In embodiments, the user input may bereceived directly at the CCCPU from the user device (e.g., via thecloud), or the user input may be received by the BSIED (e.g., through alocal connection to the BSIED), and transmitted to the CCCPU from theBSIED. Expert tuning of parameters may result from personnel familiarwith energy modeling adjusting for biases in the BSID used to create theBSOM that are unknown to the CCCPU. For example, if the BSID used tocreate the most recent BSOM included a significant interruption inactivity in the modeled building as a result of planned or unplanneddowntime, an expert operator may adjust the resulting model parametersto remove the influence of the atypical data.

At block 820, the CCCPU may also transmit the new or updated parametersto the BSIED for updating the current BSOM, and/or transmit the messageindicating which parameters should be removed from the current BSOM, tothe BSIED for updating the BSOM. In response to receiving the new orupdated parameters, or the message, the BSIED may update the BSOM.Alternatively, the CCCPU may update the BSOM on the CCCPU, and transmitthe updated BSOM to the BSIED. The updated BSOM may be stored on amemory device of the BSIED, and be used by the BSIED for processingbuilding signature inputs to generate BSOD.

Alternatively, at block 825, after having determined that the currentBSOM cannot be updated to the proposed BSOM, the CCCPU may generate anew BSOM (or retrieve the proposed BSOM, and use the proposed BSOM asthe new BSOM). At block 830, the CCCPU transmits the new BSOM (i.e., theproposed BSOM) to the BSIED. The new BSOM may be stored on a memorydevice of the BSIED, and be used by the BSIED for processing buildingsignature inputs to generate BSOD.

Returning now to block 810, if the CCCPU determines that the BSIED doesnot support the proposed BSOM, the method proceeds to block 835 wherethe CCCPU determines if the proposed BSOM can be translated into a formthe BSIED supports. For example, a BSOM intended for a relativelycomplex BSIED (e.g., an “advanced” BSIED) may be translated into a formsuitable for a less complex BSIED (e.g., a “basic” or “intermediate”BSIED). For example, the BSOM intended for the relatively complex BSIEDmay be responsive to a first plurality of building signature inputs,while the simpler BSIED is responsive to a second plurality of buildingsignature inputs that is less than the first plurality of buildingsignature inputs. In some embodiments, the BSOM can be translated (ormodified) to work with the simpler BSIED (and second plurality ofbuilding signature inputs).

In embodiments, a basic BSIED may, for example, only respond to outdoorweather temperature while an intermediate BSIED may run a model withstill only temperature as a driver, but could use one set ofcoefficients for weekdays and another for weekends. An advanced BSIEDmight support a full list of drivers, such as outdoor weathertemperature, number of occupants on a given day, production activitymetrics specific to the activity in the building (units manufactured ina manufacturing business), hours of sunlight per day, wind speed, andrelative humidity, for example, as well as be able to switch betweenversions of the models (sets of driver parameters) based onworking/nonworking hours as well as a work week/weekend/holidaycalendar, for example.

If the CCCPU determines that the proposed BSOM can be translated into aform the BSIED supports, the method proceeds to a block 840.Alternatively, if the CCCPU determines that the proposed BSOM cannot betranslated into a form the BSIED supports, the method proceeds to ablock 850.

At block 840, the CCCPU translates the proposed BSOM into a form theBSIED (i.e., generates a new operational model). Additionally, at block845, the CCCPU transmits the translated (or new) operational model tothe BSIED. The new BSOM may be stored on a memory device of the BSIED,and be used by the BSIED for processing building signature inputs togenerate BSOD.

Alternatively, at block 850, after having determined that the proposedBSOM cannot be translated into a form the BSIED supports, the CCCPU maydetermine that the BSIED should keep using the current BSOM. In someembodiments, the CCCPU may generate and transmit a message ornotification to the BSIED indicating that the BSIED should keep usingthe current BSOM.

In embodiments, the method 800 may end after blocks 820, 830, 845 or850. The method ending may, for example, be indicative of a BSOM havingbeen selected for the BSIED.

Referring now to FIG. 9, a flowchart illustrates an example method 900for managing processing of BSOD generated by a BSIED (e.g., 111, shownin FIG. 1). In embodiments, the method 900 can be implemented on theBSIED, for example.

As illustrated in FIG. 9, the method 900 begins at block 905 where theBSIED determines if an Internet connection is available. If the BSIEDdetermines that there is an Internet connection available, the methodproceeds to a block 910. Alternatively, if the BSIED determines that anInternet connection is not available, the method proceeds to a block945.

At block 910, the BSIED determines if the BSOD should be processedlocally (e.g., on the BSIED or on a cloud-connected hub communicativelycoupled to the BSIED) and/or in the cloud (e.g., on a CCCPU). If theBSIED determines that the BSOD should be processed locally, the methodproceeds to a block 945 where the BSOD is processed locally, forexample, to generate output data. In embodiments, the output data may betransmitted to an output device (e.g., a display device, for viewing bya user). Additionally, in embodiments the output data may correspond to,or be used to generate, a control signal (e.g., a control signal forcontrolling building equipment to which the BSIED is coupled).

For example, in a BSOM that is fed forecast data for the drivers (e.g.,tomorrow's weather), the BSOD generated by the BSIED may be an estimateof future energy consumption. This information may constitute a controlsignal that might be used to control the amount of energy retrieved frombattery storage for a facility or otherwise signal energy systems toprepare for a certain level of demand in the coming day. Applications ofthis kind gain a particular advantage from being able to operatecorrectly when the system is disconnected from the cloud for securityreasons or unplanned interruptions in cloud communications.

In some embodiments, it may be preferable to process at least at portionof the BSOD locally. For example, it may be preferable to process atleast at portion of the BSOD locally in embodiments in which the BSOM isa relatively simple operational model, and processing the BSOD locallyon the BSIED is quicker than processing the BSOD remotely in the cloud.Additionally, it may be preferable to process at least a portion of theBSOD locally in embodiments in which data security is a concern. Inparticular, by processing the BSOD locally, the operational data may beless susceptible to being compromised (e.g., accessed and modified) byunwanted sources (e.g., since the BSOD does not leave the premises).Further, it may be preferable to process at least a portion of the BSODlocally in embodiments in which the BSOD is used to control processes(or equipment) on the premises, for example, through a control signal,as discussed above.

Alternatively, at block 910, if the BSIED determines that the BSODshould be processed in the cloud, the method proceeds to a block 920where the BSOD is transmitted to the cloud (e.g., the CCCPU) for remoteprocessing, for example, to generate output data (or a new BSOM for theBSIED). In embodiments, the BSIED may determine that the BSOD should betransmitted to the cloud when processing the BSOD locally would impactperformance of the BSIED (e.g., due to the local processing occupyingsubstantial processing resources of the BSIED).

Alternatively, at block 910, if the BSIED determines that the BSODshould be processed both locally and in the cloud, the method proceedsto blocks 925 and 935. At block 925, the BSIED identifies portions ofthe BSOD that should be processed locally. In embodiments, the portionsmay be identified based on BSIED (or other local device) capabilities.For example, an “advanced” BSIED with robust processing capabilities maybe able to process a substantial portion of the BSOD, while a “basic”BSIED with less processing capabilities than the “advanced” BSIED mayonly be able to process a small portion of the BSOD. At block 930, theBSIED (or other local device) processes the identified portions of theBSOD. In embodiments, the identified portions of the BSOD may beprocessed to generate output data.

At block 935, the BSIED identifies portions of the BSOD that should beprocessed in the cloud. In embodiments, model computation in the cloudis only necessary when there is cloud accessible data that the BSIEDdoes not have access to. The cloud accessible data may include, forexample, community-derived data about other facilities that the CCCPUhas access to, but which the on-site BSIED does not. At block 940, theBSOD is transmitted to the cloud (e.g., the CCCPU) for remoteprocessing, for example, to generate output data (or a new BSOM for theBSIED).

Returning now to block 905, after having determined that an Internetconnection is not available, the method proceeds to a block 945. Atblock 945, the BSIED determines if at least a portion of the BSOD can beprocessed locally (e.g., on the BSIED or on a cloud-connected hubcommunicatively coupled to the BSIED). If the BSIED determines that atleast a portion of the BSOD can be processed locally, the methodproceeds to a block 950. Alternatively, if the BSIED determines that theBSOD cannot be processed locally (e.g., due to device constraints), themethod may return to block 905 and the method may be repeated.

At block 950, the BSIED identifies portions of the BSOD that can beprocessed locally. Additionally, at block 955, the BSIED (or other localdevice) processes the identified portions of the BSOD. In embodiments,the identified portions of the BSOD may be processed to generate outputdata.

At block 960, subsequent to blocks 915, 920, 930, 940 or 955, the BSIEDdetermines if there is more BSOD to be processed. If the BSIEDdetermines that there is more BSOD to be processed, for example, due tocertain portions of the BSOD needing to be processed remotely (e.g., ona CCCPU), the method returns to block 905. Alternatively, if the BSIEDdetermines that there is no more BSOD to be processed, the method 900may end. The method ending may, for example, be indicative of all of theBSOD having been processed. In embodiments, the method 900 may berepeated continuously, periodically, or in response to a control signal(e.g., a control signal as may be provided to the BSIED) depending onsystem and application requirements. For example, in embodiments themethod 900 may repeat each time new BSOD is generated by the BSIED.

Referring to FIG. 10, a plot 1000 illustrates predicted energyconsumption (e.g., daily energy consumption) for an example building(e.g., 102, shown in FIG. 1) in which a BSIED (e.g., 112, shown inFIG. 1) may be installed. The plot 1000 has a horizontal axis with ascale in temperature units (e.g., degrees Celsius (C)) and a verticalaxis with a scale in energy consumption units (e.g., kilowatt hours(kWHs)). The horizontal axis may, for example, be illustrative ofexample temperatures (e.g., average outdoor temperatures) to which thebuilding is exposed.

In embodiments, the BSIED may be responsive to temperature data receivedfrom one or more temperature sensors (e.g., 131, shown in FIG. 1) on thepremises of the building, and/or from external data sources (e.g., 190,shown in FIG. 1), such as the United States National Weather Service, toestimate the building energy consumption over various temperatures, asshown by line 1005 in plot 1000. More particularly, the temperature datamay be received as building signature input data at an input of theBSIED, and the BSIED, using the building signature input data as inputsto a BSOM associated with the BSIED, may generate building signatureoperational data (BSOD) indicative of the estimated building energyconsumption (as shown by line 1005) at an output of the BSIED. Inembodiments in which the temperature data corresponds to averagetemperature data, and the BSIED is responsive to temperature datareceived from temperature sensors on the premises of the building, theaverage outdoor temperature may, for example, be computed locally on theBSIED or remotely in the cloud (e.g., on a CCCPU). The average outdoortemperature may correspond to the average outdoor temperature at thebuilding over a predetermined time period, for example, a day, a week ora month during a particular season of the year (e.g., fall or spring).

In embodiments, the temperature data is but one of many potential inputsthat may be received as building signature input data at an input of theBSIED, and used by the BSOM of the BSIED to estimate building energyconsumption. For example, as discussed in figures above, BSOMs used byBSIEDs to generate BSOD may account for a building's typical response tovarious environmental conditions (e.g., temperature, occupancy, andother drivers).

In some embodiments, the BSOM can be used to monitor for unexpectedenergy consumption in the building for which the BSOM was created. Forexample, when building energy consumption deviates significantly fromhistorical behavior as captured in the BSOM, an alert or notificationindicating the detected deviation may be generated. In some embodiments,the alert or notification may be generated by the BSIED and indicated inthe form of a light emitting diode or other visual indicator of theBSIED. Additionally, in some embodiments the alert or notification maybe generated by the BSIED and transmitted, for example, to a user deviceof facility management personnel in the building. The facilitymanagement personnel viewing the user device can, for example, respondto the alert by shutting down equipment (or adjusting parametersassociated with equipment) (e.g., BE 122, shown in FIG. 1) in thebuilding identified by the BSIED as causing the detected deviation.

In other embodiments, user interaction is not required for shutting down(or adjusting parameters associated with equipment). The BSIED can, forexample, shut down equipment (or adjust parameters associated withequipment) in response to the detected deviation. In embodiments, theBSIED shuts down the equipment (or adjusts parameters associated withthe equipment) by generating a control signal at an output of the BSIEDin response to the detected deviation, and providing the control signalto a respective control input (or inputs) of the equipment. Aftershutting down the equipment (or adjusting parameters associated with theequipment), a notification can be sent to the user device of thefacility management personnel indicating which equipment was shut down(or which parameters associated with the equipment were adjusted).

The detected deviations may also be stored in a memory device (e.g., amemory device of the BSIED) for later analysis in some embodiments. Forexample, the detected deviations may be analyzed for determining orvalidating equipment lifetime, or for determining a particular type ofstress condition (e.g., over temperature condition) to which theequipment exposed. The particular type of stress condition may bedetermined (on the BSIED or externally), for example, by comparingmonitored values of the detected deviations (e.g., a first deviationvalue, a second deviation value, etc.) over a predetermined time period,and associating the compared values with the stress condition type. Inembodiments, the stress condition type may be reported through a displaydevice or output signal (of the BSIED or externally), for example.

Referring to FIG. 11, a plot 1100 illustrates predicted energyconsumption (e.g., daily energy consumption) for an example building(e.g., 102, shown in FIG. 1) in which a BSIED (e.g., 112, shown inFIG. 1) may be installed. The plot 1100 has a horizontal axis with ascale in occupancy units and a vertical axis with a scale in energyconsumption units (e.g., kilowatt hours (kWHs)). The horizontal axismay, for example, be illustrative of example numbers of people in thebuilding.

In embodiments, the BSIED may be responsive to occupancy data receivedfrom one or more occupancy sensors (e.g., 131, shown in FIG. 1) on thepremises of the building to estimate the building energy consumptionover various building occupancy levels, as shown by line 1105 in plot1100. More particularly, the occupancy data may be received as buildingsignature input data at an input of the BSIED, and the BSIED, using thebuilding signature input data as inputs to a BSOM associated with theBSIED, may generate BSOD indicative of the estimated building energyconsumption (as shown by line 1105) at an output of the BSIED.

As illustrated, building energy consumption is affected by buildingoccupancy. In embodiments, such occurs by virtue of additional demandsplaced on equipment (e.g., HVAC equipment) in the building in responseto increased occupancy levels. The two sets of points shown in plot 1100(as indicated by arrows 1104, 1106) represent an example unoccupied (orsubstantially unoccupied) state of the building (as indicated by arrow1104) and an example occupied state of the building (as indicated byarrow 1106). In some embodiments, the variability shown between the twoset of points is a result (sometimes, solely the result) of occupancyand random factors (the variability due to temperature has been removedand is represented in plot 1000 shown in FIG. 10). In embodiments, eachpoint corresponds to one days worth of energy use. As illustrated,building energy consumption is greater (i.e., the cluster of points ishigher) on days when the building is occupied (as indicated by arrow1106) than on days when the building is unoccupied (or substantiallyunoccupied) (as indicated by arrow 1104).

As described above and as will be appreciated by those of ordinary skillin the art, embodiments of the disclosure herein may be configured as asystem, method, or combination thereof. Accordingly, embodiments of thepresent disclosure may be comprised of various means including hardware,software, firmware or any combination thereof.

It is to be appreciated that the concepts, systems, circuits andtechniques sought to be protected herein are not limited to use inparticular applications. For example, while building signatureintelligent electronic devices, building signature operational models,etc. are described herein, it is understood that embodiments of thedisclosure are not limited to use in building signature applications.Rather, in embodiments the concepts, systems, circuits and techniquessought to be protected herein may adapted for use in substantially anyother application in which the concepts, systems, circuits andtechniques may be found suitable. For example, embodiments of thedisclosure may be found suitable for use in demand response applicationsand energy storage applications (e.g., to optimize use of energy storagesystems and associated components, such as batteries).

Having described preferred embodiments, which serve to illustratevarious concepts, structures and techniques that are the subject of thispatent, it will now become apparent to those of ordinary skill in theart that other embodiments incorporating these concepts, structures andtechniques may be used. Additionally, elements of different embodimentsdescribed herein may be combined to form other embodiments notspecifically set forth above.

Accordingly, it is submitted that that scope of the patent should not belimited to the described embodiments but rather should be limited onlyby the spirit and scope of the following claims.

What is claimed is:
 1. A method for evaluating a building signatureoperational model (BSOM) associated with a building signatureintelligent electronic device (BSIED), the method comprising: processingbuilding signature operational data (BSOD) on a cloud-connected centralprocessing unit to identify the BSIED from which the BSOD was receivedfrom, and to determine if a current BSOM associated with the BSIED, andused by the BSIED to generate the BSOD, needs to be updated; in responseto determining that the current BSOM needs to be updated, selecting anew BSOM for the BSIED based, at least in part, on one or morecharacteristics associated with the BSIED; and transmitting the new BSOMto the BSIED for installation on the BSIED.
 2. The method of claim 1further comprising validating that the new BSOM was correctlytransmitted to the BSIED.
 3. The method of claim 1 further comprisingprocessing building signature input data (BSID) using the new BSOM togenerate BSOD associated with the new BSOM, and evaluating accuracy ofthe BSOD to confirm that the new BSOM is operating as expected.
 4. Themethod of claim 3 wherein the BSID is received from one or more buildingsignature data sources (BSDSs).
 5. The method of claim 4 wherein theBSDSs comprise equipment to which the BSIED is coupled, and the BSIDcomprises energy usage information associated with the BSDSs.
 6. Themethod of claim 3 wherein the BSID corresponds to test BSID forvalidating accuracy of the BSOM.
 7. The method of claim 1 whereinprocessing BSOD on a cloud-connected central processing unit to identifythe BSIED from which the BSOD was received from, and to determine if acurrent BSOM associated with the BSIED needs to be updated, comprises:determining if a predetermined time period or other predeterminedcondition has occurred since the current BSOM has last been updated orverified; in response to determining that the predetermined time periodor other predetermined condition has occurred, submitting a requestsignal to the BSIED for retrieving BSOD from the BSIED; transmittingBSOD from the BSIED to the cloud-connected central processing unit; andprocessing the BSOD on the cloud-connected central processing unit toidentify the BSIED from which the BSOD was received from, and todetermine if a current BSOM associated with the BSIED needs to beupdated.
 8. The method of claim 1 wherein processing BSOD on acloud-connected central processing unit to determine if a current BSOMassociated with the BSIED needs to be updated comprises: comparing aversion number of an algorithm used to generate the current BSOM with aversion number of a latest model generating algorithm, and determiningthat the current BSOM needs to be updated if the version number of thealgorithm used to generate the current BSOM is substantially differentfrom the version number of the latest model generating algorithm.
 9. Themethod of claim 1 wherein selecting a new BSOM for the BSIED comprisesgenerating a new BSOM for the BSIED based, at least in part, on the BSODand one or more characteristics associated with the BSIED.
 10. Themethod of claim 1 wherein selecting a new BSOM for the BSIED comprises:selecting a closest BSOM for the BSIED from a BSOM library based, atleast in part, on one or more characteristics associated with the BSIED;determining if the closest BSOM needs to be translated or otherwisemodified to work with the BSIED; in response to determining that theclosest BSOM needs to be translated or otherwise modified to work withthe BSIED, translating the closest BSOM into a form the BSIED supports;and selecting the translated BSOM as the new BSOM for the BSIED.
 11. Themethod of claim 10 wherein the BSOM library is stored on a memory deviceassociated with the cloud-connected central processing unit, and whereinthe BSOM library comprises a plurality of BSOMs.
 12. The method of claim11 wherein the plurality of BSOMs are generated by the cloud-connectedcentral processing unit in response to receiving input data from one ormore respective data sources associated with the BSIEDs for which theplurality of BSOMs are intended.
 13. The method of claim 12 wherein thedata sources include at least one of a temperature sensor, a humiditysensor, and an occupancy sensor configured to generate respectivetemperature, humidity and occupancy input data pertaining to theenvironment(s) in which the BSIEDs are installed.
 14. The method ofclaim 1 wherein the characteristics associated with the BSIED includeBSIED type, BSIED complexity, and building signature parametersmonitored by the BSIED.
 15. The method of claim 14 wherein the BSIEDtype includes at least one of an energy meter, a power quality monitor,a waveform monitor, a programmable sensing device, an uninterruptiblepower supply, a power quality correction device, and a harmonic filterwith metering capabilities.
 16. The method of claim 15, wherein thebuilding signature parameters include one or more energy consumptionparameters.
 17. The method of claim 16 wherein the BSOD is indicative ofan estimated energy consumption of a building in which the BSIED isinstalled.
 18. The method of claim 14 wherein the BSIED complexity isselected from “basic”, “intermediate”, and “advanced”, wherein anintermediate complexity BSIED has more functionality than a basiccomplexity BSIED, and an advanced complexity BSIED has morefunctionality than the intermediate complexity BSIED.
 19. The method ofclaim 18 wherein the intermediate complexity BSIED is responsive to morebuilding signature data sources than the basic complexity BSIED, and theadvanced complexity BSIED is responsive to more building signature datasources than the intermediate complexity BSIED.
 20. The method of claim1 further comprising: subsequent to selecting the new BSOM for theBSIED, determining if the current BSOM is capable of being updated tothe new BSOM; in response to determining that the current BSOM iscapable of being updated to the new BSOM, identifying parameters to beadded to, removed from and/or modified in the current BSOM to update thecurrent BSOM to the new BSOM; and updating the current BSOM to the newBSOM based on the identified parameters.
 21. The method of claim 20wherein updating the current BSOM to the new BSOM comprises generatingthe parameters identified to be added to and/or modified in the currentBSOM, and wherein transmitting the new BSOM to the BSIED comprises: (a)transmitting the generated parameters to the BSIED, (b) providing anindication of which parameters, if any, should be removed from thecurrent BSOM to the BSIED, and (c) updating the current BSOM to the newBSOM on the BSIED based on the generated parameters and the providedindication.
 22. The method of claim 1 further comprising tuning the newBSOM in response to user input.
 23. The method of claim 22 wherein thenew BSOM is tuned on the BSIED.
 24. The method of claim 22 wherein thenew BSOM is tuned on the cloud-connected central processing unit.
 25. Abuilding signature system, comprising: at least one building signatureintelligent electronic device (BSIED) comprising a memory device and aprocessor coupled to the memory device, the processor and the memorydevice configured to: receive building signature input data (BSID) fromone or more building signature data sources (BSDSs); process thereceived BSID using a current building signature operational model(BSOM) stored on the memory device to generate building signatureoperational data (BSOD); and transmit the BSOD to a cloud-connectedcentral processing unit communicatively coupled to the at least oneBSIED; the cloud-connected central processing unit configured to:process the BSOD to identify the at least one BSIED from which the BSODwas received from, and to determine if the current BSOM associated withthe at least one BSIED needs to be updated; in response to determiningthat the current BSOM needs to be updated, select a new BSOM for the atleast one BSIED based, at least in part, on one or more characteristicsassociated with the at least one BSIED; and transmit the new BSOM to theat least one BSIED for installation on the at least one BSIED.
 26. Thebuilding signature system of claim 25, wherein the BSDSs compriseequipment to which the at least one BSIED is coupled, and the BSIDcomprises energy usage information associated with the BSDSs.
 27. Thebuilding signature system of claim 25, wherein the BSOD is indicative ofan estimated energy consumption of a building in which the at least oneBSIED is installed.